An internship form asks for your portfolio link, and you pause. You've never had a job. Your best work is a spreadsheet, a presentation and a class essay. Can those count? Yes, if you show what you did and make the work easy to understand.
Quick 60-Second Summary
Select genuine coursework for the reader you want to reach. Explain the problem, your contribution, evidence, limits and next improvement for each project. Use clear file links or a README, credit collaborators and check that the shared version contains no passwords or private information.
I'd start with those assignments before planning a brand-new project. You already know the question and the choices you made. A portfolio gives someone a closer look than a list of subjects or software names can: here's the task, here's my contribution, and here's what happened.
Three examples are enough. They needn't look professional or pretend to be paid experience. The aim is to give a teacher, mentor or internship reviewer something specific to discuss with you.
1. Choose three projects for the person reading
Before opening a website builder, read the application or assignment brief. What does this reader need to see? A coding mentor might look for understandable code and checks. A science teacher might look for measurements and explanations. Write down three relevant abilities, then look for work that shows them.
- Choose a project with a clear question and an output you can show.
- Include different kinds of work, such as a calculation, an argument and a team project.
- Pick things you can explain without reading a script.
- Check that your school allows you to share the assignment.
Give each choice a one-sentence reason. "This spreadsheet checks totals against sample inputs" tells the reader more than "This looks impressive." If two projects show much the same thing, swap one out or explain what made the second challenge different. More uploads aren't automatically more useful.
2. Give each project a one-page story
Start with what you were trying to solve. Then explain your tools, method and constraints, show the result, and finish with something you'd change. Keep it concrete. Instead of "I learned teamwork," describe how you divided the research, settled a disagreement or checked that everyone's figures used the same units.
My advice is to spend as much care on the explanation as the screenshot. A colourful chart looks tidy, but the reader still needs to know where the numbers came from and what you did with them.
- Add the date, course and time spent on the project.
- Make your part of a team assignment clear.
- Show a small data sample, screenshot or before-and-after comparison.
- Credit sources, collaborators, templates and any AI help you used.
Use demonstration data instead of classmates' real grades, and label it as made-up data. Keep private messages and restricted teaching materials out of the files. Ask before sharing another person's name or image. You can explain a project well without putting somebody else's details on the page.
Next Student Guide to Read: How to Break a Big School Assignment into Manageable Steps
3. Make it easy to open and keep up to date
Build a simple index: a short introduction, three project links and a suitable way to contact you. Put the most relevant piece first. Give files useful names and add captions that tell the reader what to notice. If the full file can be shared, link it, but make sure the one-page explanation still makes sense without downloading anything.
- Test every link while signed out.
- Read the PDF on both a phone and a laptop.
- Check screenshots and files for passwords, keys or personal records.
- Add a version date and check access before each application.
I'd choose a straightforward PDF if it gets the work ready sooner. A website can come later. If you're comfortable with repository files, GitHub Pages may suit a coding project; check the sharing settings before using it. The format should help someone see your work, not use up the weekend you meant to spend finishing it.
| Format | Best student stream | Setup time | Best for showing | How to share it |
|---|---|---|---|---|
| GitHub repository / Pages | Coding or data | 2 - 4 hours if files are ready | Code, README, sample results | Public repository or Pages URL |
| Public Notion page | Mixed subjects | 1 - 2 hours | Short case studies and embedded files | Published page link; test access |
| Google Sites page | Science, humanities or teams | 1 - 3 hours | Visual project index and documents | Published site URL |
| Single-file PDF | Any stream; offline applications | 1 - 2 hours | A concise, fixed selection | Attach or send a view-only file link |
Worked example: three projects in six hours
Take Sana, a first-year student in this example. She's got three completed assignments and six hours to turn them into a portfolio. She allows 30 minutes for choosing files, 75 per project page, 45 for the index and 60 for checking. That's 30 + 225 + 45 + 60 = 360 minutes. She's packaging existing work here; building three new projects would need its own time.
Project 1: show a calculation and its checks
Her first piece is a grade-and-expense tracker made with Python or a spreadsheet. She keeps the two examples on separate sheets and uses invented figures. Scores of 72, 81 and 87 give an unweighted mean of 80. She labels that clearly so nobody mistakes it for a weighted course grade. On the expense sheet, a INR 1,000 budget minus INR 240 for travel and INR 160 for supplies leaves INR 600.
The interesting bit is a small mistake: the first version treated a missing grade as zero. Sana shows the test that caught it and explains the fix. I wouldn't hide that correction; it gives the reader something concrete to ask about.
Project 2: explain the evidence behind a research brief
Her second piece is a 1,500-word research brief in science or economics. The portfolio page names the question, links the sources and shows a four-row table with units and dates. She identifies her calculations and explains why two things moving together doesn't prove one caused the other. A short extract and a permitted copy of the brief are enough. The index doesn't need the whole essay pasted into it.
Project 3: identify your contribution to group work
Her third piece is a group presentation, shared with permission through a view-only link. Sana identifies the four slides she researched and adds a rehearsal note showing why the group simplified a crowded chart. She credits the other members' work and leaves one open question for a future version.
Before sending the link, she asks a friend to find each project's goal and her contribution within a minute. If the friend gets lost, Sana fixes the heading, link name or explanation. That's a small check she can act on straight away.
Need help getting the sharing settings right? Use the instructions for GitHub Pages, Notion publishing or Google Sites sharing. Then open your finished link while signed out and check what the reader can actually see.
Still missing a finished piece? Break it down with the assignment milestone method. If you're looking for a course project, compare the online course formats before signing up. Or use the guide to turning an idea into a student project to get a small idea moving.
What should a five-part README.md tell a reviewer?
For a coding project, a README.md can act as its project page. Use these five sections so the reader can understand the purpose, your contribution and how to check the result without guessing.
| README section | Include | Check |
|---|---|---|
| Problem and outcome | One-sentence purpose and a demo or screenshot | A visitor can identify what the project does |
| Visual evidence | A relevant screenshot or architecture sketch | Remove private information and label illustrative material |
| Tools and contribution | Libraries, hardware, and your role | Do not claim a teammate's implementation |
| Reproduction | Dependencies, sample data, and run instructions | Test the steps in a fresh environment |
| Reflection | One limitation, decision, and next improvement | Make the explanation specific and honest |
Credit collaborators and external material. Remove passwords, private records and secret keys from anything you share. If someone cannot follow the instructions, revise them before linking the project from an application.
Questions students ask
Can coursework count if I have no job experience?
Yes. Explain the assignment context and show your own work. Make your contribution and limitations clear rather than presenting a class exercise as paid employment.
How many projects should I start with?
Choose a small selection you can explain clearly. Three is a workable starting example in this guide, not a rule; prioritise relevance and evidence over volume.
What belongs in a project README?
State its purpose, show evidence, identify tools and contributions, explain how to open or reproduce it, and note one limitation or next improvement.
Related Student Guides
- How to Break a Big School Assignment into Manageable Steps
- A Practical Study System for Digital and Paper Notes
- How Spreadsheet Formulas Help Students Track Grades and Lab Data
0 Comments